Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72652399b4006379fc1dc0bd202235f277d7ad1210904bbfc23b9eda32a5e1d0

Tx prefix hash: ac0d6b6726c84fa6cdad6abeaf27aec3ea5aaa2fc913ede014b3ac6f7c36d4b8
Tx public key: f5d1254e31d9a1047b38c8e4f70f02884f7bc29937c614ec0aaa62dc539e59eb
Timestamp: 1725211956 Timestamp [UCT]: 2024-09-01 17:32:36 Age [y:d:h:m:s]: 00:214:08:04:25
Block: 1100768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153025 RingCT/type: yes/0
Extra: 01f5d1254e31d9a1047b38c8e4f70f02884f7bc29937c614ec0aaa62dc539e59eb021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21bce7cef0fc5bb2fcbff47ca629b5cf0fb6083480940b58ca5dbfacab38d2c6 0.600000000000 1576749 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": 1100778, "vin": [ { "gen": { "height": 1100768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21bce7cef0fc5bb2fcbff47ca629b5cf0fb6083480940b58ca5dbfacab38d2c6" } } ], "extra": [ 1, 245, 209, 37, 78, 49, 217, 161, 4, 123, 56, 200, 228, 247, 15, 2, 136, 79, 123, 194, 153, 55, 198, 20, 236, 10, 170, 98, 220, 83, 158, 89, 235, 2, 17, 0, 0, 0, 3, 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