Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d6ebe70e22b9200751a437dca2e24ef2dc82a6db487623f7c8de158753f319a5

Tx prefix hash: bbdd9528bc7b5827e668eceb5d5fe54b94a272747fcd34efd4bfce861b0b155b
Tx public key: f325209dbb6561654353beab301da815e0abf4f0e340f23c6361a9ed46feadb6
Timestamp: 1624228393 Timestamp [UCT]: 2021-06-20 22:33:13 Age [y:d:h:m:s]: 03:201:16:40:25
Block: 281270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910984 RingCT/type: yes/0
Extra: 01f325209dbb6561654353beab301da815e0abf4f0e340f23c6361a9ed46feadb60211000000ea65496328000000000000000000

1 output(s) for total of 71.787900203000 dcy

stealth address amount amount idx
00: 69076c4954d0b4d0a6e7cc67ce14fdbf1d6df34f40abab8c697b0cd74fe009f5 71.787900203000 588965 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 281280, "vin": [ { "gen": { "height": 281270 } } ], "vout": [ { "amount": 71787900203, "target": { "key": "69076c4954d0b4d0a6e7cc67ce14fdbf1d6df34f40abab8c697b0cd74fe009f5" } } ], "extra": [ 1, 243, 37, 32, 157, 187, 101, 97, 101, 67, 83, 190, 171, 48, 29, 168, 21, 224, 171, 244, 240, 227, 64, 242, 60, 99, 97, 169, 237, 70, 254, 173, 182, 2, 17, 0, 0, 0, 234, 101, 73, 99, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8