Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd423fa056452bf1a3c6a019213cac04aead3b7aea8510ff6dd715f65bf5ba8

Tx prefix hash: ab3ea5ed4a270f62e96bcd8910dd73a8052cc0c870247cbe41c7cb97b575746c
Tx public key: 7dae8d2dcf111761465aeea7cc3d21d91a29579812cd5c8d3d480d28abfe04fa
Timestamp: 1724037895 Timestamp [UCT]: 2024-08-19 03:24:55 Age [y:d:h:m:s]: 00:221:07:20:41
Block: 1091040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158028 RingCT/type: yes/0
Extra: 017dae8d2dcf111761465aeea7cc3d21d91a29579812cd5c8d3d480d28abfe04fa021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a099e52f228a771ff2dcd726648c6795e9fc3fbe75ac368920741d559ec5ebdc 0.600000000000 1565665 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": 1091050, "vin": [ { "gen": { "height": 1091040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a099e52f228a771ff2dcd726648c6795e9fc3fbe75ac368920741d559ec5ebdc" } } ], "extra": [ 1, 125, 174, 141, 45, 207, 17, 23, 97, 70, 90, 238, 167, 204, 61, 33, 217, 26, 41, 87, 152, 18, 205, 92, 141, 61, 72, 13, 40, 171, 254, 4, 250, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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