Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96024da533c760f5ffd885e8ff841216c8e0f24dd845e743b0bbf3708b8b511d

Tx prefix hash: 4bfad26c41bf7471e6a48d84936852a64dc79475c086ad5d6f8acade2756bdc8
Tx public key: ea8f38fa74e3a24496fd3b4c37c1db84c2594389c533965c88cb103ecf50e0d3
Timestamp: 1728597436 Timestamp [UCT]: 2024-10-10 21:57:16 Age [y:d:h:m:s]: 00:212:17:18:25
Block: 1128832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151841 RingCT/type: yes/0
Extra: 01ea8f38fa74e3a24496fd3b4c37c1db84c2594389c533965c88cb103ecf50e0d302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baed26f5dadcdea498dd9633cf3168a95954ebe2bdecf9c320af8784388ea1e9 0.600000000000 1611655 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": 1128842, "vin": [ { "gen": { "height": 1128832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baed26f5dadcdea498dd9633cf3168a95954ebe2bdecf9c320af8784388ea1e9" } } ], "extra": [ 1, 234, 143, 56, 250, 116, 227, 162, 68, 150, 253, 59, 76, 55, 193, 219, 132, 194, 89, 67, 137, 197, 51, 150, 92, 136, 203, 16, 62, 207, 80, 224, 211, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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