Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d325ddd1239887c623f7ab9314fb1be5b568fcfd8a6e6505b8e4b717c56bf597

Tx prefix hash: 5103cc24b817027e2a949242cc5a0f36fd8ec5b42d9ed69f71e8d57ca80841da
Tx public key: 3624a61ffef6bbc8db5fe922859fb1a2fb4a9bfa6ab8f970247a0b1ef91ca412
Timestamp: 1703883429 Timestamp [UCT]: 2023-12-29 20:57:09 Age [y:d:h:m:s]: 01:102:17:05:14
Block: 923934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334529 RingCT/type: yes/0
Extra: 013624a61ffef6bbc8db5fe922859fb1a2fb4a9bfa6ab8f970247a0b1ef91ca4120211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c0bfc763f6ef3ea55ce792192302612a493e7513306b89f235f6fdf476536e 0.600000000000 1381672 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": 923944, "vin": [ { "gen": { "height": 923934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c0bfc763f6ef3ea55ce792192302612a493e7513306b89f235f6fdf476536e" } } ], "extra": [ 1, 54, 36, 166, 31, 254, 246, 187, 200, 219, 95, 233, 34, 133, 159, 177, 162, 251, 74, 155, 250, 106, 184, 249, 112, 36, 122, 11, 30, 249, 28, 164, 18, 2, 17, 0, 0, 0, 1, 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