Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9b62546a0fe04777928c1197b0e691bfabd1ba7d2d5316e9e157d1441f47b44

Tx prefix hash: b96064ae636b2c327109b47c544d1a7e9edae6a6dafb169d3a51fd724155c9dc
Tx public key: c5788ff1326b67ba002683bcb35bf6a03f8c51e7f275d34ded4b3a766afc6bc4
Timestamp: 1712163077 Timestamp [UCT]: 2024-04-03 16:51:17 Age [y:d:h:m:s]: 00:263:00:27:08
Block: 992560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188335 RingCT/type: yes/0
Extra: 01c5788ff1326b67ba002683bcb35bf6a03f8c51e7f275d34ded4b3a766afc6bc40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 257fdcdb80c7c136bbb9e9ca8704dfd7561b0c49158af180d1287133db652de2 0.600000000000 1452914 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": 992570, "vin": [ { "gen": { "height": 992560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257fdcdb80c7c136bbb9e9ca8704dfd7561b0c49158af180d1287133db652de2" } } ], "extra": [ 1, 197, 120, 143, 241, 50, 107, 103, 186, 0, 38, 131, 188, 179, 91, 246, 160, 63, 140, 81, 231, 242, 117, 211, 77, 237, 75, 58, 118, 106, 252, 107, 196, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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