Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a7d5ee67d3217fe5203663e3f4ad42d9d0d65656492a1dd53c2c93e6793631e

Tx prefix hash: 7fd4f7060d80d74a420ac76a23d6ef7a3f4b3fc1ca8ab68f804b9c5a1caa0f1e
Tx public key: f710274f6dea4cd4000000837107351d84aa7c6bdf865230a4b9e5076b1f0315
Timestamp: 1719112798 Timestamp [UCT]: 2024-06-23 03:19:58 Age [y:d:h:m:s]: 00:281:05:07:25
Block: 1050180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200960 RingCT/type: yes/0
Extra: 01f710274f6dea4cd4000000837107351d84aa7c6bdf865230a4b9e5076b1f031502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0b54bdd9d14a4e975b691370f50c6292c6ec5ff89351e26d8cf89c1660464c 0.600000000000 1520341 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": 1050190, "vin": [ { "gen": { "height": 1050180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0b54bdd9d14a4e975b691370f50c6292c6ec5ff89351e26d8cf89c1660464c" } } ], "extra": [ 1, 247, 16, 39, 79, 109, 234, 76, 212, 0, 0, 0, 131, 113, 7, 53, 29, 132, 170, 124, 107, 223, 134, 82, 48, 164, 185, 229, 7, 107, 31, 3, 21, 2, 17, 0, 0, 0, 1, 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