Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6316f47a9f13c0fb4bac5be1f1df777192995331b53d596b2376f36ae7198ecb

Tx prefix hash: a33a7629281b33f125a309d5aaa5bbfa666b9b20046673266f6641850db0fb42
Tx public key: 739f94adfaaba9b1281810a1babc7e5eb72676a0da8f1e453c97d253198baf3b
Timestamp: 1577523611 Timestamp [UCT]: 2019-12-28 09:00:11 Age [y:d:h:m:s]: 05:044:04:53:37
Block: 33305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181531 RingCT/type: yes/0
Extra: 01739f94adfaaba9b1281810a1babc7e5eb72676a0da8f1e453c97d253198baf3b021100000107ac34bf9e000000000000000000

1 output(s) for total of 476.044516439000 dcy

stealth address amount amount idx
00: 0b3556e8c805f44b2bb2e27387f7768aba4c4cab66a62033963490635f6b7f37 476.044516439000 55734 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": 33315, "vin": [ { "gen": { "height": 33305 } } ], "vout": [ { "amount": 476044516439, "target": { "key": "0b3556e8c805f44b2bb2e27387f7768aba4c4cab66a62033963490635f6b7f37" } } ], "extra": [ 1, 115, 159, 148, 173, 250, 171, 169, 177, 40, 24, 16, 161, 186, 188, 126, 94, 183, 38, 118, 160, 218, 143, 30, 69, 60, 151, 210, 83, 25, 139, 175, 59, 2, 17, 0, 0, 1, 7, 172, 52, 191, 158, 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