Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668ff53a45696f264d856067656710f6e348bb687e52b73780bf3f6ca6dfe396

Tx prefix hash: 132141641bfb666fad6d25b24aaec31c6a2199093db7df33edc12d1e3956ef98
Tx public key: 544f1da8d76ca6b9887bf39a085d27a1515fdf8d3da0e01896fae924969c674f
Timestamp: 1688364584 Timestamp [UCT]: 2023-07-03 06:09:44 Age [y:d:h:m:s]: 01:198:23:49:49
Block: 795546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403571 RingCT/type: yes/0
Extra: 01544f1da8d76ca6b9887bf39a085d27a1515fdf8d3da0e01896fae924969c674f021100000001faf35c9c000000000000000000

1 output(s) for total of 1.419142452000 dcy

stealth address amount amount idx
00: 8830c54b0cd8ca416e4e4bf2266d5b08e819f14ba609fc5dab14d8e37282732c 1.419142452000 1246359 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": 795556, "vin": [ { "gen": { "height": 795546 } } ], "vout": [ { "amount": 1419142452, "target": { "key": "8830c54b0cd8ca416e4e4bf2266d5b08e819f14ba609fc5dab14d8e37282732c" } } ], "extra": [ 1, 84, 79, 29, 168, 215, 108, 166, 185, 136, 123, 243, 154, 8, 93, 39, 161, 81, 95, 223, 141, 61, 160, 224, 24, 150, 250, 233, 36, 150, 156, 103, 79, 2, 17, 0, 0, 0, 1, 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