Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efcce2b2592f4605a5ad5a8ebefc80f6c1952cc1f274760e0f74471d06990f5b

Tx prefix hash: e8e79d73a1aa66eb22c494a8cd898c728867942908c3de85f0c2fbda11f6f0a5
Tx public key: 0cdd8c06711281ad701d747aec9baf36219f9e4f9a3e7053f372af33cfab5eba
Timestamp: 1708521258 Timestamp [UCT]: 2024-02-21 13:14:18 Age [y:d:h:m:s]: 01:042:11:04:43
Block: 962392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291374 RingCT/type: yes/0
Extra: 010cdd8c06711281ad701d747aec9baf36219f9e4f9a3e7053f372af33cfab5eba0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1fc06e62b43aedf54bed602b5428838cb7a90585336c3849bd4cbf3a94d5e91 0.600000000000 1422027 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": 962402, "vin": [ { "gen": { "height": 962392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1fc06e62b43aedf54bed602b5428838cb7a90585336c3849bd4cbf3a94d5e91" } } ], "extra": [ 1, 12, 221, 140, 6, 113, 18, 129, 173, 112, 29, 116, 122, 236, 155, 175, 54, 33, 159, 158, 79, 154, 62, 112, 83, 243, 114, 175, 51, 207, 171, 94, 186, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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