Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b65c8d28afa8d361c8c096127e9c4edfd80af9c6283d677a3ace44aaf1f2209f

Tx prefix hash: fc9d800c255b414e6304cd9e1961f8a6870de7f836b15e3839a8a10a7af4d993
Tx public key: 8909e683cec9ab8b87f3d42d51f9d657898609eb4af9d516436399e7b2a032fb
Timestamp: 1576643180 Timestamp [UTC]: 2019-12-18 04:26:20 Age [y:d:h:m:s]: 06:150:21:18:33
Block: 28084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1506693 RingCT/type: yes/0
Extra: 018909e683cec9ab8b87f3d42d51f9d657898609eb4af9d516436399e7b2a032fb02110000003c9159db1e000000000000000000

1 output(s) for total of 0.495389634127 xmr

stealth address amount amount idx tag
00: 9754eccb8bd2ad4aed7ab78c3d11c8a938984da3413614388b695b72f3191586 0.495389634127 46606 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 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": 28094, "vin": [ { "gen": { "height": 28084 } } ], "vout": [ { "amount": 495389634127, "target": { "key": "9754eccb8bd2ad4aed7ab78c3d11c8a938984da3413614388b695b72f3191586" } } ], "extra": [ 1, 137, 9, 230, 131, 206, 201, 171, 139, 135, 243, 212, 45, 81, 249, 214, 87, 137, 134, 9, 235, 74, 249, 213, 22, 67, 99, 153, 231, 178, 160, 50, 251, 2, 17, 0, 0, 0, 60, 145, 89, 219, 30, 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: