Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 397e6bac9fd292dc86b9e18335d23ad58983c08e8beddde80627c3718b514add

Tx prefix hash: a60c44c8e992fb9240d2b8675d4ed2d8df877fe443c9893f9e202c2e4a81d257
Tx public key: bf92f00ad0bf28e04a6576cad9ae538e7ec58148fc5a8b5dfb07363794178c34
Timestamp: 1701909215 Timestamp [UCT]: 2023-12-07 00:33:35 Age [y:d:h:m:s]: 01:133:18:46:16
Block: 907573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356773 RingCT/type: yes/0
Extra: 01bf92f00ad0bf28e04a6576cad9ae538e7ec58148fc5a8b5dfb07363794178c34021100000004faf35c9c000000000000000000

1 output(s) for total of 0.603717649000 dcy

stealth address amount amount idx
00: 699216027498df771e77b662df54a36818aead4146387d6dcf4f768ddcebbf88 0.603717649000 1364566 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": 907583, "vin": [ { "gen": { "height": 907573 } } ], "vout": [ { "amount": 603717649, "target": { "key": "699216027498df771e77b662df54a36818aead4146387d6dcf4f768ddcebbf88" } } ], "extra": [ 1, 191, 146, 240, 10, 208, 191, 40, 224, 74, 101, 118, 202, 217, 174, 83, 142, 126, 197, 129, 72, 252, 90, 139, 93, 251, 7, 54, 55, 148, 23, 140, 52, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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