Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02429deffa8c3f9bce4136fa1e06495cad1c9c7c58f7aff0af7bdbda87f041e7

Tx prefix hash: 98c13e881ede52631743253d1d2c6873147fc866e8dc15ecc6de66dbcaa94dea
Tx public key: cf4af34f3e2b4b77240e82b2699445b91fa3832f7122f5dde8806497cc96f0c3
Timestamp: 1732751951 Timestamp [UCT]: 2024-11-27 23:59:11 Age [y:d:h:m:s]: 00:128:03:23:31
Block: 1163179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91386 RingCT/type: yes/0
Extra: 01cf4af34f3e2b4b77240e82b2699445b91fa3832f7122f5dde8806497cc96f0c30211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ceac28ce907e90e345c41cfd3d3bdcace7b15a92e286b8cb3a19d669b86ac25 0.600000000000 1648846 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": 1163189, "vin": [ { "gen": { "height": 1163179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ceac28ce907e90e345c41cfd3d3bdcace7b15a92e286b8cb3a19d669b86ac25" } } ], "extra": [ 1, 207, 74, 243, 79, 62, 43, 75, 119, 36, 14, 130, 178, 105, 148, 69, 185, 31, 163, 131, 47, 113, 34, 245, 221, 232, 128, 100, 151, 204, 150, 240, 195, 2, 17, 0, 0, 0, 6, 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