Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a5d8b83e2f41553d289994300ad4695d291307a7a445781d407906a4f33acbe

Tx prefix hash: ef7b55a859d9bd80a2dc499b92aeb21d4c9d2293566df9d099c0bc9c5e3151f7
Tx public key: 7fdd1a2a3d351cec2149b932a40a11faa188a85f178b683b0dc8ce68cef89989
Timestamp: 1694768300 Timestamp [UCT]: 2023-09-15 08:58:20 Age [y:d:h:m:s]: 01:199:01:28:22
Block: 848554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403356 RingCT/type: yes/0
Extra: 017fdd1a2a3d351cec2149b932a40a11faa188a85f178b683b0dc8ce68cef89989021100000009faf35c9c000000000000000000

1 output(s) for total of 0.947083794000 dcy

stealth address amount amount idx
00: 43e407f032a4d271a7ee897b5c93cf9d99b7dcc95c26aea4e116645c67f8a55c 0.947083794000 1302166 of 0

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": 848564, "vin": [ { "gen": { "height": 848554 } } ], "vout": [ { "amount": 947083794, "target": { "key": "43e407f032a4d271a7ee897b5c93cf9d99b7dcc95c26aea4e116645c67f8a55c" } } ], "extra": [ 1, 127, 221, 26, 42, 61, 53, 28, 236, 33, 73, 185, 50, 164, 10, 17, 250, 161, 136, 168, 95, 23, 139, 104, 59, 13, 200, 206, 104, 206, 248, 153, 137, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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