Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb0fc9de93985711225dde0efe739f19b84f982c071dbf26effaae7f3b861ec

Tx prefix hash: efdc13189db70e176c11571396e33be27f7fa9da1925188ef403efd8618ede9f
Tx public key: 0b1a0ab0f25c4b29b81d7bfbca1e265191b45cecef578468790bb2458efab300
Timestamp: 1753859486 Timestamp [UTC]: 2025-07-30 07:11:26 Age [y:d:h:m:s]: 00:288:07:49:28
Block: 1336483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197200 RingCT/type: yes/0
Extra: 010b1a0ab0f25c4b29b81d7bfbca1e265191b45cecef578468790bb2458efab300021100000002ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65d1feca51c8d6a0537fb056f727e9af25295e1f3ea7343bd706e52063b876de 0.000600000000 1824284 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": 1336493, "vin": [ { "gen": { "height": 1336483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d1feca51c8d6a0537fb056f727e9af25295e1f3ea7343bd706e52063b876de" } } ], "extra": [ 1, 11, 26, 10, 176, 242, 92, 75, 41, 184, 29, 123, 251, 202, 30, 38, 81, 145, 180, 92, 236, 239, 87, 132, 104, 121, 11, 178, 69, 142, 250, 179, 0, 2, 17, 0, 0, 0, 2, 239, 34, 20, 133, 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: