Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd3def602edc4dbac9ec5d72cc566e1ac09b953ba69c1d91492f0c4ac692906

Tx prefix hash: 70c4c00b72f485ffb0162dd21a8ae4d79ea15d2c10c2604cdc8e338a0c4be55e
Tx public key: a61585b820ca673dfde8133d13d4218dc3a37ccd3e96839c9c29e235d7198d02
Timestamp: 1729985373 Timestamp [UCT]: 2024-10-26 23:29:33 Age [y:d:h:m:s]: 00:233:17:12:49
Block: 1140311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166761 RingCT/type: yes/0
Extra: 01a61585b820ca673dfde8133d13d4218dc3a37ccd3e96839c9c29e235d7198d02021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21cca663f8f0660d79e847273440c32383a93eef51ae67089e83ced19a2c85da 0.600000000000 1624106 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": 1140321, "vin": [ { "gen": { "height": 1140311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21cca663f8f0660d79e847273440c32383a93eef51ae67089e83ced19a2c85da" } } ], "extra": [ 1, 166, 21, 133, 184, 32, 202, 103, 61, 253, 232, 19, 61, 19, 212, 33, 141, 195, 163, 124, 205, 62, 150, 131, 156, 156, 41, 226, 53, 215, 25, 141, 2, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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