Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ffe5df64d8d3891e858880c2224861c6a22c49bad7f93898972a1830335640

Tx prefix hash: a047c1ab6e77b40f9fc946e496cb33e59f75eb5b032bde4f9b0d3a6bf63b7fa6
Tx public key: 7bf5222ba1ec6a504963ad8860a13b9fc16efae1946ed75f5d637c5c2cac2139
Timestamp: 1713714943 Timestamp [UCT]: 2024-04-21 15:55:43 Age [y:d:h:m:s]: 00:249:00:44:59
Block: 1005444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178252 RingCT/type: yes/0
Extra: 017bf5222ba1ec6a504963ad8860a13b9fc16efae1946ed75f5d637c5c2cac213902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1606ef54b3d48894b9e0b6811ec5053ad3b750c8461e0b84d8eee3fe085b458 0.600000000000 1466132 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": 1005454, "vin": [ { "gen": { "height": 1005444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1606ef54b3d48894b9e0b6811ec5053ad3b750c8461e0b84d8eee3fe085b458" } } ], "extra": [ 1, 123, 245, 34, 43, 161, 236, 106, 80, 73, 99, 173, 136, 96, 161, 59, 159, 193, 110, 250, 225, 148, 110, 215, 95, 93, 99, 124, 92, 44, 172, 33, 57, 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