Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4880a9677d5004721e2611618886e81140a6d64749ed631b6145b51779f5fe9

Tx prefix hash: d7afb4ab224459154f37039317ed0d2580c2d0861569b9eaf5305927dca2f2fb
Tx public key: 62533186fffb6d03b3b52b28a9d6569ed5bb1b8d92f64e4b5c7dedd9a3100ff9
Timestamp: 1728526786 Timestamp [UCT]: 2024-10-10 02:19:46 Age [y:d:h:m:s]: 00:104:07:45:57
Block: 1128246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74529 RingCT/type: yes/0
Extra: 0162533186fffb6d03b3b52b28a9d6569ed5bb1b8d92f64e4b5c7dedd9a3100ff9021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 423ef4ec2edaeac696ab1613e14ab40a4ddaf033b375caa6385ddd5a8b03b952 0.600000000000 1611063 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": 1128256, "vin": [ { "gen": { "height": 1128246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "423ef4ec2edaeac696ab1613e14ab40a4ddaf033b375caa6385ddd5a8b03b952" } } ], "extra": [ 1, 98, 83, 49, 134, 255, 251, 109, 3, 179, 181, 43, 40, 169, 214, 86, 158, 213, 187, 27, 141, 146, 246, 78, 75, 92, 125, 237, 217, 163, 16, 15, 249, 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