Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1933cf0a5cdb3f3fe33a96b5c3089fe7e5b14237874420c7e1905add72a0ea

Tx prefix hash: 26e661812919d30b434d85e610ea6b851a04ef2dbd0d83a7c900c05cf2f6be03
Tx public key: 901dd46f5160485a5424f05bff7a226aafd5aab8948b5c0217f3165e6bcb29dc
Timestamp: 1717671600 Timestamp [UCT]: 2024-06-06 11:00:00 Age [y:d:h:m:s]: 00:361:15:57:37
Block: 1038263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258514 RingCT/type: yes/0
Extra: 01901dd46f5160485a5424f05bff7a226aafd5aab8948b5c0217f3165e6bcb29dc02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64dfd566164b17a98f6c6e7aa23e6032b13dcfdf4ad8c549d0311ffe8ff3a208 0.600000000000 1506824 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": 1038273, "vin": [ { "gen": { "height": 1038263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64dfd566164b17a98f6c6e7aa23e6032b13dcfdf4ad8c549d0311ffe8ff3a208" } } ], "extra": [ 1, 144, 29, 212, 111, 81, 96, 72, 90, 84, 36, 240, 91, 255, 122, 34, 106, 175, 213, 170, 184, 148, 139, 92, 2, 23, 243, 22, 94, 107, 203, 41, 220, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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