Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02145af3cda30d95524b17b08a515277852ed0487d923e762f57f9a87deb03cf

Tx prefix hash: bb1918fa062491afdeb04b63b988bcbae4db1adfa8bbc8ba602ef3f9b3155d0d
Tx public key: c56878e60ad1e7b7de3134f1e0258ff6cbc216b9afb9b7662f47e58a52f02533
Timestamp: 1728865221 Timestamp [UCT]: 2024-10-14 00:20:21 Age [y:d:h:m:s]: 00:174:16:57:47
Block: 1131054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124632 RingCT/type: yes/0
Extra: 01c56878e60ad1e7b7de3134f1e0258ff6cbc216b9afb9b7662f47e58a52f02533021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e58c3aab860f53a3c7ef807d231a38dcd5cb8fddf1f98fff95082670cbe714c9 0.600000000000 1613935 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": 1131064, "vin": [ { "gen": { "height": 1131054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e58c3aab860f53a3c7ef807d231a38dcd5cb8fddf1f98fff95082670cbe714c9" } } ], "extra": [ 1, 197, 104, 120, 230, 10, 209, 231, 183, 222, 49, 52, 241, 224, 37, 143, 246, 203, 194, 22, 185, 175, 185, 183, 102, 47, 71, 229, 138, 82, 240, 37, 51, 2, 17, 0, 0, 0, 1, 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