Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77a0fc528aa2e5356253312ccf0500287514bd48e1cd79fae3178d7447ac894

Tx prefix hash: 08f22aa4810d7e8ce7965320a09172f2b0abf7e6ac53a0d5db5e407a21b2206b
Tx public key: 6f236da16246774929b434c81a62a11c4f1ccff0bb16094faa2b773496218bad
Timestamp: 1712604482 Timestamp [UTC]: 2024-04-08 19:28:02 Age [y:d:h:m:s]: 02:040:19:56:13
Block: 996213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542130 RingCT/type: yes/0
Extra: 016f236da16246774929b434c81a62a11c4f1ccff0bb16094faa2b773496218bad02110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 677e5d2a25336f5d6628b1ae8735232a5c58a9c2b8df9ddefdf4b84c43d95789 0.000600000000 1456629 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 dinastycoin-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": 996223, "vin": [ { "gen": { "height": 996213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "677e5d2a25336f5d6628b1ae8735232a5c58a9c2b8df9ddefdf4b84c43d95789" } } ], "extra": [ 1, 111, 35, 109, 161, 98, 70, 119, 73, 41, 180, 52, 200, 26, 98, 161, 28, 79, 28, 207, 240, 187, 22, 9, 79, 170, 43, 119, 52, 150, 33, 139, 173, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: