Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87b846d3e3c9e9b849ec1c2f8ebbb7e584781c97afe907f5d4e986cddebfb537

Tx prefix hash: 747e783884d6305ac658453b221cc752511bd62fc6a304c60b3eeed844d5aa30
Tx public key: 9a6c2796030c3c862f5241b782ec84a4e5db289bcd38b1daddc788abb05abc9a
Timestamp: 1708021091 Timestamp [UCT]: 2024-02-15 18:18:11 Age [y:d:h:m:s]: 01:010:23:13:44
Block: 958240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268847 RingCT/type: yes/0
Extra: 019a6c2796030c3c862f5241b782ec84a4e5db289bcd38b1daddc788abb05abc9a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6b58b32dd842cdf3cf9242c80c6eee3055b03db7dc08595a11b9ffb819d8908 0.600000000000 1417599 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": 958250, "vin": [ { "gen": { "height": 958240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6b58b32dd842cdf3cf9242c80c6eee3055b03db7dc08595a11b9ffb819d8908" } } ], "extra": [ 1, 154, 108, 39, 150, 3, 12, 60, 134, 47, 82, 65, 183, 130, 236, 132, 164, 229, 219, 40, 155, 205, 56, 177, 218, 221, 199, 136, 171, 176, 90, 188, 154, 2, 17, 0, 0, 0, 2, 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