Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854c43ffd9aef1daa8e111a29f956374664c5eb325912a991e4f21fafdb1efb8

Tx prefix hash: 23af2f2bc1ef7c75f1815ef16d85ebeeec12ef7a1a2162dbce79e7ab263423bd
Tx public key: bfb006f808d27fd9d40568a475e3156ec138f1a8c6e67dcd3e23de42896c70ef
Timestamp: 1574686895 Timestamp [UCT]: 2019-11-25 13:01:35 Age [y:d:h:m:s]: 05:036:02:41:53
Block: 17166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168644 RingCT/type: yes/0
Extra: 01bfb006f808d27fd9d40568a475e3156ec138f1a8c6e67dcd3e23de42896c70ef021100000001f95225a5000000000000000000

1 output(s) for total of 538.422000153000 dcy

stealth address amount amount idx
00: 926c9e6aa03b3d9cd6b1f97c776a6e070de50b72de86b1be4900ccabc9d102cf 538.422000153000 24641 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": 17176, "vin": [ { "gen": { "height": 17166 } } ], "vout": [ { "amount": 538422000153, "target": { "key": "926c9e6aa03b3d9cd6b1f97c776a6e070de50b72de86b1be4900ccabc9d102cf" } } ], "extra": [ 1, 191, 176, 6, 248, 8, 210, 127, 217, 212, 5, 104, 164, 117, 227, 21, 110, 193, 56, 241, 168, 198, 230, 125, 205, 62, 35, 222, 66, 137, 108, 112, 239, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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