Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7ef0fa44954aebdc2f8453b70838c3d839a6aaf564885d2fab1dd9e23385b3

Tx prefix hash: 6d13cc8ab2691f681734534f9c38120f66301c9e950469a28f2bb073912814b9
Tx public key: 17c403dc667e85753b9b275c392575f377dfb4512d6c30e2dd9054cc6af06bf6
Timestamp: 1740926660 Timestamp [UCT]: 2025-03-02 14:44:20 Age [y:d:h:m:s]: 00:264:09:43:47
Block: 1230580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186727 RingCT/type: yes/0
Extra: 0117c403dc667e85753b9b275c392575f377dfb4512d6c30e2dd9054cc6af06bf60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c11305a7373041ebca4a68211e2a032d092cc92dfd07abf09b82c68de3879aa1 0.600000000000 1717479 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": 1230590, "vin": [ { "gen": { "height": 1230580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c11305a7373041ebca4a68211e2a032d092cc92dfd07abf09b82c68de3879aa1" } } ], "extra": [ 1, 23, 196, 3, 220, 102, 126, 133, 117, 59, 155, 39, 92, 57, 37, 117, 243, 119, 223, 180, 81, 45, 108, 48, 226, 221, 144, 84, 204, 106, 240, 107, 246, 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