Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8807b505bbc070e5233dc14501222ec08602905603d1db7b6b1a7b18219a0ae

Tx prefix hash: 01867fb1d953ef5c0318d573ba0d303de470a010d1ca3ac090c26b9711901f00
Tx public key: 9f95fe9cc3d06aff0af36c4904e47bf9429f17dea29d1a3a9750a76f302f629b
Timestamp: 1764959071 Timestamp [UCT]: 2025-12-05 18:24:31 Age [y:d:h:m:s]: 00:010:17:32:09
Block: 1427145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7693 RingCT/type: yes/0
Extra: 019f95fe9cc3d06aff0af36c4904e47bf9429f17dea29d1a3a9750a76f302f629b02110000000cd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6e713070b37a127b7b3b02c574f68f91e93a2610e95ad7380e379b8d52415c 0.600000000000 1915844 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": 1427155, "vin": [ { "gen": { "height": 1427145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6e713070b37a127b7b3b02c574f68f91e93a2610e95ad7380e379b8d52415c" } } ], "extra": [ 1, 159, 149, 254, 156, 195, 208, 106, 255, 10, 243, 108, 73, 4, 228, 123, 249, 66, 159, 23, 222, 162, 157, 26, 58, 151, 80, 167, 111, 48, 47, 98, 155, 2, 17, 0, 0, 0, 12, 214, 225, 157, 124, 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