Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab56d25ef8c41a63ff0a584679f5fd9924abf5d95b4fe29639e79162f3aecfa

Tx prefix hash: 963ef19060d52d963fda80d4062483e2cdd450caec702af6be3beb0ac40554d5
Tx public key: 056e3c1459c2cf2a9ea9a45b1d800c3433a1888996efc705d026e86d992e1aa8
Timestamp: 1710339484 Timestamp [UCT]: 2024-03-13 14:18:04 Age [y:d:h:m:s]: 01:252:11:15:49
Block: 977483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439133 RingCT/type: yes/0
Extra: 01056e3c1459c2cf2a9ea9a45b1d800c3433a1888996efc705d026e86d992e1aa802110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0973414967108bb5053acb37b8605bbfedfd23877897b37feb4e9e0407aa0a02 0.600000000000 1437486 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": 977493, "vin": [ { "gen": { "height": 977483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0973414967108bb5053acb37b8605bbfedfd23877897b37feb4e9e0407aa0a02" } } ], "extra": [ 1, 5, 110, 60, 20, 89, 194, 207, 42, 158, 169, 164, 91, 29, 128, 12, 52, 51, 161, 136, 137, 150, 239, 199, 5, 208, 38, 232, 109, 153, 46, 26, 168, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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