Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d2a236856ca7bfec553212197732fec27adf5060a5ece3918c991d913f2855

Tx prefix hash: 177dee85289c22452d44297d85e7d237e75b51c76357bc148d464a01fd1f6bc2
Tx public key: df20aa9c4513e932a6bf1f361c0e4a3d9d9a816a9d73ece2568061a52f68eccf
Timestamp: 1713047528 Timestamp [UCT]: 2024-04-13 22:32:08 Age [y:d:h:m:s]: 01:057:08:53:36
Block: 999895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302013 RingCT/type: yes/0
Extra: 01df20aa9c4513e932a6bf1f361c0e4a3d9d9a816a9d73ece2568061a52f68eccf02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e667f5158dd43181b34d48f04830620556beb4ed9b9f2e8feb2f6df362cf06ac 0.600000000000 1460383 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": 999905, "vin": [ { "gen": { "height": 999895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e667f5158dd43181b34d48f04830620556beb4ed9b9f2e8feb2f6df362cf06ac" } } ], "extra": [ 1, 223, 32, 170, 156, 69, 19, 233, 50, 166, 191, 31, 54, 28, 14, 74, 61, 157, 154, 129, 106, 157, 115, 236, 226, 86, 128, 97, 165, 47, 104, 236, 207, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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