Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d950651169985dfd51da85cf1fb3a9c6ed0b1d2b4317e571b5a22669374157c9

Tx prefix hash: b58598aa9641ac141bec69c8f3570239c976a2390ce439a989da811c485caf2e
Tx public key: b0c68cba5754ff6ef3c3981508d1fed81dc0ead407ec745a2d96b69ef0e831a2
Timestamp: 1732665334 Timestamp [UCT]: 2024-11-26 23:55:34 Age [y:d:h:m:s]: 01:008:19:00:47
Block: 1162463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264702 RingCT/type: yes/0
Extra: 01b0c68cba5754ff6ef3c3981508d1fed81dc0ead407ec745a2d96b69ef0e831a2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75b2a8be5333fc8bd5ec27fb79ab4e3912bfb7b1df5fb5e50ed3cd832eb42ce5 0.600000000000 1648120 of 15

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": 1162473, "vin": [ { "gen": { "height": 1162463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75b2a8be5333fc8bd5ec27fb79ab4e3912bfb7b1df5fb5e50ed3cd832eb42ce5" } } ], "extra": [ 1, 176, 198, 140, 186, 87, 84, 255, 110, 243, 195, 152, 21, 8, 209, 254, 216, 29, 192, 234, 212, 7, 236, 116, 90, 45, 150, 182, 158, 240, 232, 49, 162, 2, 17, 0, 0, 0, 1, 0, 127, 151, 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