Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d35b394c49886f3318704eea4e5e96ff3f269ac8426457e4b16b90ba841ac87

Tx prefix hash: 630ec6ea25f4b418c1f00d043b186a1b3ec51d54f6b0be11e57de4b6905b9fc8
Tx public key: 3826697a7fee16f6bcefa7e2187039897007a3de16d7c4c7d33cf09e363082ba
Timestamp: 1717117400 Timestamp [UCT]: 2024-05-31 01:03:20 Age [y:d:h:m:s]: 01:172:13:09:14
Block: 1033660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381911 RingCT/type: yes/0
Extra: 013826697a7fee16f6bcefa7e2187039897007a3de16d7c4c7d33cf09e363082ba0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a149b06c3ca3a6966e968a5a0583e6a4108d775d8d11beff109e1dcb2fecb7 0.600000000000 1502131 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": 1033670, "vin": [ { "gen": { "height": 1033660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a149b06c3ca3a6966e968a5a0583e6a4108d775d8d11beff109e1dcb2fecb7" } } ], "extra": [ 1, 56, 38, 105, 122, 127, 238, 22, 246, 188, 239, 167, 226, 24, 112, 57, 137, 112, 7, 163, 222, 22, 215, 196, 199, 211, 60, 240, 158, 54, 48, 130, 186, 2, 17, 0, 0, 0, 2, 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