Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae3327340a7406228b244377e6e6afcc28712619dbcaf07a38392cb80b3a2e9

Tx prefix hash: 73faf4c0632c945896c5345653f79b9111fb5e71bb1849200b30bc1da041ca91
Tx public key: a6a0d9f7a45c77779b0dc3df1d0f3d4c6451ee2917a391b152f303a7896d9be5
Timestamp: 1726571819 Timestamp [UCT]: 2024-09-17 11:16:59 Age [y:d:h:m:s]: 00:178:13:31:19
Block: 1112036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127453 RingCT/type: yes/0
Extra: 01a6a0d9f7a45c77779b0dc3df1d0f3d4c6451ee2917a391b152f303a7896d9be5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fa7015be5fe3cf588e50ef2838b7d43ad9e82e1c5d781eeb7b31f931b03e6f3 0.600000000000 1591211 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": 1112046, "vin": [ { "gen": { "height": 1112036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fa7015be5fe3cf588e50ef2838b7d43ad9e82e1c5d781eeb7b31f931b03e6f3" } } ], "extra": [ 1, 166, 160, 217, 247, 164, 92, 119, 119, 155, 13, 195, 223, 29, 15, 61, 76, 100, 81, 238, 41, 23, 163, 145, 177, 82, 243, 3, 167, 137, 109, 155, 229, 2, 17, 0, 0, 0, 6, 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