Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9cb54c2f40cbcd4d5f1ed0b169adffd82ffda6cc7de791bb7f8186f5270405c

Tx prefix hash: ec8f2a7ea217544ad5a5bb47c3b07f38483805a2be4e342cc984060edc17ee63
Tx public key: b1f2faefc334d1fbc92361893dd26e4294b530e9cd32e0631f21b9503aa24f95
Timestamp: 1592761255 Timestamp [UCT]: 2020-06-21 17:40:55 Age [y:d:h:m:s]: 04:190:08:19:07
Block: 110188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074503 RingCT/type: yes/0
Extra: 01b1f2faefc334d1fbc92361893dd26e4294b530e9cd32e0631f21b9503aa24f9502110000003246a11e8a000000000000000000

1 output(s) for total of 264.790355421000 dcy

stealth address amount amount idx
00: c231f6922bfeeafbc7a11ea30aae51b9d5b05d2a0f94b04643d82cf5e1e33e59 264.790355421000 190824 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": 110198, "vin": [ { "gen": { "height": 110188 } } ], "vout": [ { "amount": 264790355421, "target": { "key": "c231f6922bfeeafbc7a11ea30aae51b9d5b05d2a0f94b04643d82cf5e1e33e59" } } ], "extra": [ 1, 177, 242, 250, 239, 195, 52, 209, 251, 201, 35, 97, 137, 61, 210, 110, 66, 148, 181, 48, 233, 205, 50, 224, 99, 31, 33, 185, 80, 58, 162, 79, 149, 2, 17, 0, 0, 0, 50, 70, 161, 30, 138, 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