Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82dfb46e69bf8a0d433fc00f020eba7a6fd1589ebb8fe7fc985bf12c9634bbf

Tx prefix hash: fdc48fd1d1b4ffc66bcc3a233f436d9521e453907628f2243a6349000ce7c5f9
Tx public key: 050292dc22f64cba611a4feb1a2d4e998f21d9eab7fe57bd2c9108fc4ba36beb
Timestamp: 1770314835 Timestamp [UTC]: 2026-02-05 18:07:15 Age [y:d:h:m:s]: 00:282:16:17:10
Block: 1471370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207458 RingCT/type: yes/0
Extra: 01050292dc22f64cba611a4feb1a2d4e998f21d9eab7fe57bd2c9108fc4ba36beb021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6d1441a3fde48e9c43dc610e8f37c0e78bf5f1c3cce9af8abc37a87ed575b83 0.000600000000 1960642 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": 1471380, "vin": [ { "gen": { "height": 1471370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6d1441a3fde48e9c43dc610e8f37c0e78bf5f1c3cce9af8abc37a87ed575b83" } } ], "extra": [ 1, 5, 2, 146, 220, 34, 246, 76, 186, 97, 26, 79, 235, 26, 45, 78, 153, 143, 33, 217, 234, 183, 254, 87, 189, 44, 145, 8, 252, 75, 163, 107, 235, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: