Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a269eb39ee6ef360b31310095808894e696c16164185a6eb03907ac4486e4056

Tx prefix hash: 1dda8e26f4407ca42e96bca4a79212da3aaf823ab5b080734b8dce799952d9fe
Tx public key: fe1068ddc6c2d27c86a3ed92b5e63f5d08c746db4db248e9ce6e1326ca610e27
Timestamp: 1733888767 Timestamp [UCT]: 2024-12-11 03:46:07 Age [y:d:h:m:s]: 00:104:07:49:43
Block: 1172610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74332 RingCT/type: yes/0
Extra: 01fe1068ddc6c2d27c86a3ed92b5e63f5d08c746db4db248e9ce6e1326ca610e27021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61af694f23d140aa7f77c2120cef7f2ad094abcb4baa4f74b916334db1891c93 0.600000000000 1658525 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": 1172620, "vin": [ { "gen": { "height": 1172610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61af694f23d140aa7f77c2120cef7f2ad094abcb4baa4f74b916334db1891c93" } } ], "extra": [ 1, 254, 16, 104, 221, 198, 194, 210, 124, 134, 163, 237, 146, 181, 230, 63, 93, 8, 199, 70, 219, 77, 178, 72, 233, 206, 110, 19, 38, 202, 97, 14, 39, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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