Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559a47d0bc2f07dc3b2483365a5ae235236ba261b88195b800379988c4e89a0e

Tx prefix hash: 2733ef57961d0d3ce7e9a60168361056b63e22996679c17f41ad6f34405f4bb2
Tx public key: a23c05e58e9c4e6f1081ca6259f9a4622010048ff4a3e4c0dcd55c97d8f20b92
Timestamp: 1705003420 Timestamp [UCT]: 2024-01-11 20:03:40 Age [y:d:h:m:s]: 01:097:12:53:06
Block: 933211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330819 RingCT/type: yes/0
Extra: 01a23c05e58e9c4e6f1081ca6259f9a4622010048ff4a3e4c0dcd55c97d8f20b920211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6daa193b177fac779655407663d9534b475546f25e85eeab367f5191fd63a644 0.600000000000 1391171 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": 933221, "vin": [ { "gen": { "height": 933211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6daa193b177fac779655407663d9534b475546f25e85eeab367f5191fd63a644" } } ], "extra": [ 1, 162, 60, 5, 229, 142, 156, 78, 111, 16, 129, 202, 98, 89, 249, 164, 98, 32, 16, 4, 143, 244, 163, 228, 192, 220, 213, 92, 151, 216, 242, 11, 146, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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