Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef0ffd615036d83e2e466cca3af5c8169954abfc39777eafcf26a3ef7fb82a7

Tx prefix hash: 506bc565c9d897a5537ee4bfccdbe2c3140bce17163ff3c5a965816f195be481
Tx public key: 54edd2d13bb4ad8d81d627fd920b5fda8f611c97a7b0d76319860c28ff6bb644
Timestamp: 1738048034 Timestamp [UCT]: 2025-01-28 07:07:14 Age [y:d:h:m:s]: 00:340:04:15:00
Block: 1206772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240952 RingCT/type: yes/0
Extra: 0154edd2d13bb4ad8d81d627fd920b5fda8f611c97a7b0d76319860c28ff6bb6440211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4746a4d86afb4d7477aa07d881acc59b120cb771229de0df1d708abbf4298f3d 0.600000000000 1693485 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": 1206782, "vin": [ { "gen": { "height": 1206772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4746a4d86afb4d7477aa07d881acc59b120cb771229de0df1d708abbf4298f3d" } } ], "extra": [ 1, 84, 237, 210, 209, 59, 180, 173, 141, 129, 214, 39, 253, 146, 11, 95, 218, 143, 97, 28, 151, 167, 176, 215, 99, 25, 134, 12, 40, 255, 107, 182, 68, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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