Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d20209530a80ac6863cc5d2fef3051da0f9f7da14f6113c0fb9b31f8a829ec56

Tx prefix hash: 2e134e0d806c99e778e0870b50393b54fabfc4852823e67e7d30d629bfdf1798
Tx public key: a03a1c04bec8e4f03c39804121a19b62f6dd0033b8bb0d379ca6dcf4134fff28
Timestamp: 1712507971 Timestamp [UCT]: 2024-04-07 16:39:31 Age [y:d:h:m:s]: 01:028:15:43:24
Block: 995406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281481 RingCT/type: yes/0
Extra: 01a03a1c04bec8e4f03c39804121a19b62f6dd0033b8bb0d379ca6dcf4134fff2802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a11ca678e31e3a1ea50d97e413669d766603d12df527b07040867b25a9b6dd0f 0.600000000000 1455814 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": 995416, "vin": [ { "gen": { "height": 995406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11ca678e31e3a1ea50d97e413669d766603d12df527b07040867b25a9b6dd0f" } } ], "extra": [ 1, 160, 58, 28, 4, 190, 200, 228, 240, 60, 57, 128, 65, 33, 161, 155, 98, 246, 221, 0, 51, 184, 187, 13, 55, 156, 166, 220, 244, 19, 79, 255, 40, 2, 17, 0, 0, 0, 3, 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