Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab23404d0013ff4c63704e80258e116ce03a10d6b6890d4b343cd99ab9323953

Tx prefix hash: 441e25a38d43edc6d388beb94f8700e397aa450e897eb8a95b8ef5c8152cddc8
Tx public key: 0de7e0ee3ff82b60e5278520ea68fc2e13a36ea693402e5a074931cd7a96ae14
Timestamp: 1700002741 Timestamp [UCT]: 2023-11-14 22:59:01 Age [y:d:h:m:s]: 01:189:12:22:14
Block: 891767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396667 RingCT/type: yes/0
Extra: 010de7e0ee3ff82b60e5278520ea68fc2e13a36ea693402e5a074931cd7a96ae1402110000000433af99f4000000000000000000

1 output(s) for total of 0.681091930000 dcy

stealth address amount amount idx
00: 265be51d013869cafefe0ccbab50b581816a3bec09831f0e037de102ea615030 0.681091930000 1347818 of 0

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": 891777, "vin": [ { "gen": { "height": 891767 } } ], "vout": [ { "amount": 681091930, "target": { "key": "265be51d013869cafefe0ccbab50b581816a3bec09831f0e037de102ea615030" } } ], "extra": [ 1, 13, 231, 224, 238, 63, 248, 43, 96, 229, 39, 133, 32, 234, 104, 252, 46, 19, 163, 110, 166, 147, 64, 46, 90, 7, 73, 49, 205, 122, 150, 174, 20, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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