Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3631557874a325252fae311e9dbd3036ee960f2d3dc86dd45a9319ca0f3fde

Tx prefix hash: a018fd5c5590ea47ace34d8b234f30d860419ed4db4d367ebbb9d9cc8e61ce81
Tx public key: 4f0988419a0f30eb7e3ffbf49ed6f0085aba33acc6c3d376ae4e4876eeccfdf6
Timestamp: 1723652122 Timestamp [UCT]: 2024-08-14 16:15:22 Age [y:d:h:m:s]: 00:276:05:00:50
Block: 1087836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197302 RingCT/type: yes/0
Extra: 014f0988419a0f30eb7e3ffbf49ed6f0085aba33acc6c3d376ae4e4876eeccfdf602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ca50d5dd21dba4fa209939632394cd8f22989d95314b31b661ae4bd419bf08 0.600000000000 1562447 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": 1087846, "vin": [ { "gen": { "height": 1087836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ca50d5dd21dba4fa209939632394cd8f22989d95314b31b661ae4bd419bf08" } } ], "extra": [ 1, 79, 9, 136, 65, 154, 15, 48, 235, 126, 63, 251, 244, 158, 214, 240, 8, 90, 186, 51, 172, 198, 195, 211, 118, 174, 78, 72, 118, 238, 204, 253, 246, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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