Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f063884781807effe38cb65fe512065c53cf1369c2dabe4b782425237f48ce

Tx prefix hash: cbc0a4c9fc00da9d9ee05a2e35d03019ad5e9e6477d4508ed6a4a094e56717e1
Tx public key: 0b76d2cd5b94b0fea2bad3fcac950cb0383bf45ac7d6ea3c2b5e6e8b535ebc5d
Timestamp: 1774411828 Timestamp [UTC]: 2026-03-25 04:10:28 Age [y:d:h:m:s]: 00:237:01:06:19
Block: 1505249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174913 RingCT/type: yes/0
Extra: 010b76d2cd5b94b0fea2bad3fcac950cb0383bf45ac7d6ea3c2b5e6e8b535ebc5d021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05ba8ec7b2bdeeecdeb61174049e3213689dbcc8893e883fdf470366a240ff4c 0.000600000000 1994981 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": 1505259, "vin": [ { "gen": { "height": 1505249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05ba8ec7b2bdeeecdeb61174049e3213689dbcc8893e883fdf470366a240ff4c" } } ], "extra": [ 1, 11, 118, 210, 205, 91, 148, 176, 254, 162, 186, 211, 252, 172, 149, 12, 176, 56, 59, 244, 90, 199, 214, 234, 60, 43, 94, 110, 139, 83, 94, 188, 93, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: