Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3676e58eae6b0be5bd347ed1212f767b9b1ff10eed3db50f30fb4d58cd09596

Tx prefix hash: c836e49e6611e9a753300e55b0691d812dfc9b6809c34f747eb0547ffc10d2c5
Tx public key: e09930fa47a375f5fd9a241430ce7b737627b13222fb8a76db2eacc0556c458e
Timestamp: 1727837781 Timestamp [UCT]: 2024-10-02 02:56:21 Age [y:d:h:m:s]: 01:075:19:12:42
Block: 1122542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312596 RingCT/type: yes/0
Extra: 01e09930fa47a375f5fd9a241430ce7b737627b13222fb8a76db2eacc0556c458e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09fd746140ec588668f2c9bb2e00d96a2641398c2433196508caf2d372c0ad59 0.600000000000 1605003 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": 1122552, "vin": [ { "gen": { "height": 1122542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09fd746140ec588668f2c9bb2e00d96a2641398c2433196508caf2d372c0ad59" } } ], "extra": [ 1, 224, 153, 48, 250, 71, 163, 117, 245, 253, 154, 36, 20, 48, 206, 123, 115, 118, 39, 177, 50, 34, 251, 138, 118, 219, 46, 172, 192, 85, 108, 69, 142, 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