Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725d92ca8e84abca2f62e1a7052ed6a830f119c91f30a4bdca913b5abcbed1a3

Tx prefix hash: c3d473daa8cfe71255bea68b4aeba676d008ebbc82c963a43922040385b66a60
Tx public key: a948d41e31e9c31087e71eb5e01108b5c5953f0d5267ed29056a3da2d60676f0
Timestamp: 1727015352 Timestamp [UCT]: 2024-09-22 14:29:12 Age [y:d:h:m:s]: 00:202:23:15:30
Block: 1115716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144883 RingCT/type: yes/0
Extra: 01a948d41e31e9c31087e71eb5e01108b5c5953f0d5267ed29056a3da2d60676f002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0f4bb6ef8b63d984773a2cdd79d744ea02cbe7d39de9a5d214819fb57069fa 0.600000000000 1595945 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": 1115726, "vin": [ { "gen": { "height": 1115716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0f4bb6ef8b63d984773a2cdd79d744ea02cbe7d39de9a5d214819fb57069fa" } } ], "extra": [ 1, 169, 72, 212, 30, 49, 233, 195, 16, 135, 231, 30, 181, 224, 17, 8, 181, 197, 149, 63, 13, 82, 103, 237, 41, 5, 106, 61, 162, 214, 6, 118, 240, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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