Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794bde40028599a6b7a5838f01f4a0fe81eabec00a1a8522a4b69ddebd4d1632

Tx prefix hash: 3c768186cc1978cd29b0fc4234a27673912aa736547ae06bb3fbddcaa7f278e1
Tx public key: 44618939d033ce1e1b23987a49c72521e7889d23d3008b6c6caaca3bbd920d75
Timestamp: 1721845528 Timestamp [UCT]: 2024-07-24 18:25:28 Age [y:d:h:m:s]: 00:327:08:22:49
Block: 1072844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233815 RingCT/type: yes/0
Extra: 0144618939d033ce1e1b23987a49c72521e7889d23d3008b6c6caaca3bbd920d7502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35cc8d8bad4c6a5a539a9cd3c191d5102d9c38cf133f1c8a343e1ef9728cf4a 0.600000000000 1545341 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": 1072854, "vin": [ { "gen": { "height": 1072844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35cc8d8bad4c6a5a539a9cd3c191d5102d9c38cf133f1c8a343e1ef9728cf4a" } } ], "extra": [ 1, 68, 97, 137, 57, 208, 51, 206, 30, 27, 35, 152, 122, 73, 199, 37, 33, 231, 136, 157, 35, 211, 0, 139, 108, 108, 170, 202, 59, 189, 146, 13, 117, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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