Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5375549bb474bc2bda046fa7fddd16b42ed2ad55d9b803e3e2bb200a3249a4

Tx prefix hash: d6fad20a91a9497fa83a92a0ea90b12c2a3f485f5f69e9d2934e1c3cb400f118
Tx public key: bbd46cfc214f561ffbe2127a05148ab8a429f9b4691d9e51f204c6f53b6306af
Timestamp: 1744073057 Timestamp [UTC]: 2025-04-08 00:44:17 Age [y:d:h:m:s]: 01:227:07:28:23
Block: 1256617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426657 RingCT/type: yes/0
Extra: 01bbd46cfc214f561ffbe2127a05148ab8a429f9b4691d9e51f204c6f53b6306af021100000001dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed7ba2e9c133409c5b27ab2a4f2331d555d64cde38f49576b9414bca379565a7 0.000600000000 1743732 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": 1256627, "vin": [ { "gen": { "height": 1256617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed7ba2e9c133409c5b27ab2a4f2331d555d64cde38f49576b9414bca379565a7" } } ], "extra": [ 1, 187, 212, 108, 252, 33, 79, 86, 31, 251, 226, 18, 122, 5, 20, 138, 184, 164, 41, 249, 180, 105, 29, 158, 81, 242, 4, 198, 245, 59, 99, 6, 175, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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: