Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b42ad2f28d1c37e15087134c61907e46f4a47d603c213974a91993d851f4321a

Tx prefix hash: cb67ff99cf8535a2c76b3f220df805089be268a5c5892c40a710c0dc649520de
Tx public key: 55a96bee40144a0d6effb9e008519fd538f4b78b14a0642571be1adefb77140f
Timestamp: 1735957924 Timestamp [UCT]: 2025-01-04 02:32:04 Age [y:d:h:m:s]: 00:169:03:52:53
Block: 1189725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120540 RingCT/type: yes/0
Extra: 0155a96bee40144a0d6effb9e008519fd538f4b78b14a0642571be1adefb77140f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e63fb691924b0aafcde699611cda3e11501ba7b4d92d5d4588edb913fd0f8d4 0.600000000000 1676236 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": 1189735, "vin": [ { "gen": { "height": 1189725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e63fb691924b0aafcde699611cda3e11501ba7b4d92d5d4588edb913fd0f8d4" } } ], "extra": [ 1, 85, 169, 107, 238, 64, 20, 74, 13, 110, 255, 185, 224, 8, 81, 159, 213, 56, 244, 183, 139, 20, 160, 100, 37, 113, 190, 26, 222, 251, 119, 20, 15, 2, 17, 0, 0, 0, 4, 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