Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd05c8163656bb6a11ed698829d7df64192c584ca6170483a65aa6ff13961179

Tx prefix hash: 96d2487b0a4329ef14fd49eadcf2f250fccdd38b1ffefcd2ad8abb6341e0e190
Tx public key: 31d6f137d2348ae88c5fd6db86468ec73a2314f5b663c25145b4f0f80c97c7d1
Timestamp: 1730783280 Timestamp [UCT]: 2024-11-05 05:08:00 Age [y:d:h:m:s]: 01:006:09:55:24
Block: 1146861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263009 RingCT/type: yes/0
Extra: 0131d6f137d2348ae88c5fd6db86468ec73a2314f5b663c25145b4f0f80c97c7d1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e7a929ced918e56b9c11ac2cc88470e9f000e0b9a0c933057acd0706587f75 0.600000000000 1631552 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": 1146871, "vin": [ { "gen": { "height": 1146861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e7a929ced918e56b9c11ac2cc88470e9f000e0b9a0c933057acd0706587f75" } } ], "extra": [ 1, 49, 214, 241, 55, 210, 52, 138, 232, 140, 95, 214, 219, 134, 70, 142, 199, 58, 35, 20, 245, 182, 99, 194, 81, 69, 180, 240, 248, 12, 151, 199, 209, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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