Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb9632c9f375ecdff61ba9ababf2afc0607cdf1ef3be88670984e6bcff64f9dc

Tx prefix hash: 61d58d20af3990f60aba96f93ab3370579178523d1c638b9f12fe05200d47b74
Tx public key: 8dd5c40f1c03f8d71a37ad07ea6349b40f024c1df279ce0d66874222c393de72
Timestamp: 1747040126 Timestamp [UTC]: 2025-05-12 08:55:26 Age [y:d:h:m:s]: 01:063:10:53:15
Block: 1281199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301144 RingCT/type: yes/0
Extra: 018dd5c40f1c03f8d71a37ad07ea6349b40f024c1df279ce0d66874222c393de720211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b56773120526d8e3bd59aa7e6ea295113dcffc669c80f829e0aab3dc1953b935 0.000600000000 1768598 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": 1281209, "vin": [ { "gen": { "height": 1281199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b56773120526d8e3bd59aa7e6ea295113dcffc669c80f829e0aab3dc1953b935" } } ], "extra": [ 1, 141, 213, 196, 15, 28, 3, 248, 215, 26, 55, 173, 7, 234, 99, 73, 180, 15, 2, 76, 29, 242, 121, 206, 13, 102, 135, 66, 34, 195, 147, 222, 114, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: