Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5941228b809182f1b5ace342eb32bf157dcd8408b1079d89a3238a9755332dc

Tx prefix hash: ed7863dee72bb2f8b59fb8915cfa512f1e068a8acaa14457cc205ec0c7470b2c
Tx public key: 21f4fba0ac381477239d22e741b4bdbeb59ee6d96e7953df3a1bfe3bccc91f3c
Timestamp: 1709343066 Timestamp [UCT]: 2024-03-02 01:31:06 Age [y:d:h:m:s]: 01:108:09:22:23
Block: 969207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338404 RingCT/type: yes/0
Extra: 0121f4fba0ac381477239d22e741b4bdbeb59ee6d96e7953df3a1bfe3bccc91f3c02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14905cab469a9133754cf9731e5595304e8f60762daa38e35d4f407b8ca1d4d9 0.600000000000 1429036 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": 969217, "vin": [ { "gen": { "height": 969207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14905cab469a9133754cf9731e5595304e8f60762daa38e35d4f407b8ca1d4d9" } } ], "extra": [ 1, 33, 244, 251, 160, 172, 56, 20, 119, 35, 157, 34, 231, 65, 180, 189, 190, 181, 158, 230, 217, 110, 121, 83, 223, 58, 27, 254, 59, 204, 201, 31, 60, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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