Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e777ada1f10ffe67b084e1338628832161cfac43a037dc0e668b670c60a045

Tx prefix hash: 68225aa4fde5708cd921ce5149a1d8112f9dab6001f9b3b88ba5d82b88569857
Tx public key: e9c70b7afb7599d90a387ed03efd0dc9e50c61c01235c6b5d1e93fb253bfcb68
Timestamp: 1726624553 Timestamp [UCT]: 2024-09-18 01:55:53 Age [y:d:h:m:s]: 00:114:03:00:17
Block: 1112471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81611 RingCT/type: yes/0
Extra: 01e9c70b7afb7599d90a387ed03efd0dc9e50c61c01235c6b5d1e93fb253bfcb68021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb75ebd550272a30993deebac70571c62c02bf476d3afdabf42df6e0ef8a116 0.600000000000 1591804 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": 1112481, "vin": [ { "gen": { "height": 1112471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb75ebd550272a30993deebac70571c62c02bf476d3afdabf42df6e0ef8a116" } } ], "extra": [ 1, 233, 199, 11, 122, 251, 117, 153, 217, 10, 56, 126, 208, 62, 253, 13, 201, 229, 12, 97, 192, 18, 53, 198, 181, 209, 233, 63, 178, 83, 191, 203, 104, 2, 17, 0, 0, 0, 2, 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