Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69408eb8cb442cc32fe38d7054dbcac65d76f55f18e3c2c0f3721b08039450f3

Tx prefix hash: 1bf8edebcd0de72172fa2703a0a504c5b6b37e2c4e4415dd8571e43bd42143cf
Tx public key: d13cfa0b3aa146e576c42e428d852574dde8a562d9ea43032c0f57ac151e5066
Timestamp: 1731404345 Timestamp [UCT]: 2024-11-12 09:39:05 Age [y:d:h:m:s]: 00:137:02:32:52
Block: 1152011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97815 RingCT/type: yes/0
Extra: 01d13cfa0b3aa146e576c42e428d852574dde8a562d9ea43032c0f57ac151e50660211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 226ded756cd8c03437b6ae9a7efc29ae6745a93ca3e7e9fa06b27bc14aca10be 0.600000000000 1637602 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": 1152021, "vin": [ { "gen": { "height": 1152011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "226ded756cd8c03437b6ae9a7efc29ae6745a93ca3e7e9fa06b27bc14aca10be" } } ], "extra": [ 1, 209, 60, 250, 11, 58, 161, 70, 229, 118, 196, 46, 66, 141, 133, 37, 116, 221, 232, 165, 98, 217, 234, 67, 3, 44, 15, 87, 172, 21, 30, 80, 102, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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