Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ebc96ee29253263f235d07318e1e28fd0806ed4cb02d94b100b4f2dec2d78ad

Tx prefix hash: 469300077c3760a956ae688cdbc4e251d759d6d093c44d04327281d497a21696
Tx public key: 9bf883c00d356ae0c4b43a1b1148ae52416379e7a359ecc5d4ccd974ec761842
Timestamp: 1727079421 Timestamp [UCT]: 2024-09-23 08:17:01 Age [y:d:h:m:s]: 00:192:17:20:00
Block: 1116250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137543 RingCT/type: yes/0
Extra: 019bf883c00d356ae0c4b43a1b1148ae52416379e7a359ecc5d4ccd974ec761842021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f06026b285085c0fce6faeb4bc89f570646d0171914bec7b525022e76376d39 0.600000000000 1596665 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": 1116260, "vin": [ { "gen": { "height": 1116250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f06026b285085c0fce6faeb4bc89f570646d0171914bec7b525022e76376d39" } } ], "extra": [ 1, 155, 248, 131, 192, 13, 53, 106, 224, 196, 180, 58, 27, 17, 72, 174, 82, 65, 99, 121, 231, 163, 89, 236, 197, 212, 204, 217, 116, 236, 118, 24, 66, 2, 17, 0, 0, 0, 7, 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