Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685bd6c4d050ec84f3625fa4555e68a0bc2b2cfa5d2ad6f968beecfde5f9e73c

Tx prefix hash: 0e3a604d1af8b8967eb4ab012f0dd87b70c07e46ceb4e642a075c5bd25a5d331
Tx public key: 066ddcf1beb2f9a5744d2d5ebd609837c438d5b6daf28b8f8ebf6cf39c0a2372
Timestamp: 1759271574 Timestamp [UTC]: 2025-09-30 22:32:54 Age [y:d:h:m:s]: 01:044:08:51:32
Block: 1380016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297959 RingCT/type: yes/0
Extra: 01066ddcf1beb2f9a5744d2d5ebd609837c438d5b6daf28b8f8ebf6cf39c0a237202110000000197baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 91235a55046cb8cbc952c52ae7399550b962fae771e41587c50e11e2841101e9 0.000600000000 1868127 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": 1380026, "vin": [ { "gen": { "height": 1380016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91235a55046cb8cbc952c52ae7399550b962fae771e41587c50e11e2841101e9" } } ], "extra": [ 1, 6, 109, 220, 241, 190, 178, 249, 165, 116, 77, 45, 94, 189, 96, 152, 55, 196, 56, 213, 182, 218, 242, 139, 143, 142, 191, 108, 243, 156, 10, 35, 114, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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: