Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1e8a96deef7e597182ccf274305a9df2ad833fe5dec83b6cdccc66da674f3e

Tx prefix hash: d1cee7bbef9099c0529b5dce5a92f012e59243fd5be7a3e902a14ed73bae53f1
Tx public key: ca3f3fed24a5e53acd587234114c4a3ba7d8b14dc144a3e81b98cd967763d043
Timestamp: 1737220510 Timestamp [UCT]: 2025-01-18 17:15:10 Age [y:d:h:m:s]: 00:152:18:24:30
Block: 1200134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108880 RingCT/type: yes/0
Extra: 01ca3f3fed24a5e53acd587234114c4a3ba7d8b14dc144a3e81b98cd967763d0430211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15b94e48fd2b3f04abf57d5f49fe2be82a16c4740bd3bbd11b3a5edfb0a187fc 0.600000000000 1686775 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": 1200144, "vin": [ { "gen": { "height": 1200134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15b94e48fd2b3f04abf57d5f49fe2be82a16c4740bd3bbd11b3a5edfb0a187fc" } } ], "extra": [ 1, 202, 63, 63, 237, 36, 165, 229, 58, 205, 88, 114, 52, 17, 76, 74, 59, 167, 216, 177, 77, 193, 68, 163, 232, 27, 152, 205, 150, 119, 99, 208, 67, 2, 17, 0, 0, 0, 6, 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