Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e965014463ed0eff30a588afd3c1065d724a680a25c36ee294c6a8213c7fea8a

Tx prefix hash: 8db27d939f78c132391b97c266db2a0692c01dcfb5f2fc8b9ad72c34303b13e4
Tx public key: bf57f7a5aeab52626fec1aa2e2bb56a66b7413f56889a5c3a3eeac0bbcfd3e13
Timestamp: 1709366634 Timestamp [UCT]: 2024-03-02 08:03:54 Age [y:d:h:m:s]: 01:035:20:28:15
Block: 969411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286609 RingCT/type: yes/0
Extra: 01bf57f7a5aeab52626fec1aa2e2bb56a66b7413f56889a5c3a3eeac0bbcfd3e130211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2480e4db237cc2ee8bd243f62112c831a7d0a6a9ecdf08e0a6f2ab15dad7fe23 0.600000000000 1429240 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": 969421, "vin": [ { "gen": { "height": 969411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2480e4db237cc2ee8bd243f62112c831a7d0a6a9ecdf08e0a6f2ab15dad7fe23" } } ], "extra": [ 1, 191, 87, 247, 165, 174, 171, 82, 98, 111, 236, 26, 162, 226, 187, 86, 166, 107, 116, 19, 245, 104, 137, 165, 195, 163, 238, 172, 11, 188, 253, 62, 19, 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