Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6556b8f802fc0c2972c75b32abdf1f1dc1e63e1fcf9c576ff2c20d59df9f8a3a

Tx prefix hash: 2e0982b011d651c70ed2c5854749e1620a98e8bdf20a223edd3068a715af54a9
Tx public key: a8901e8ff1c25d782646e9b53c3666efe34fd7c2845cabf673c4dd772a44b8c3
Timestamp: 1761998187 Timestamp [UTC]: 2025-11-01 11:56:27 Age [y:d:h:m:s]: 01:013:19:26:56
Block: 1402645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276082 RingCT/type: yes/0
Extra: 01a8901e8ff1c25d782646e9b53c3666efe34fd7c2845cabf673c4dd772a44b8c302110000000325a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3bee8f06ec2d91216a70182f4803f3cfc18859f55f74214d027d96b320746f99 0.000600000000 1890964 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": 1402655, "vin": [ { "gen": { "height": 1402645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bee8f06ec2d91216a70182f4803f3cfc18859f55f74214d027d96b320746f99" } } ], "extra": [ 1, 168, 144, 30, 143, 241, 194, 93, 120, 38, 70, 233, 181, 60, 54, 102, 239, 227, 79, 215, 194, 132, 92, 171, 246, 115, 196, 221, 119, 42, 68, 184, 195, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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: