Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43d22e7b413601bc98e806bcec6aac92ecbcf74dd46ce5ec05e64ca1af3e7cb6

Tx prefix hash: 09a7b0aa952510f37eff3af71286fc3052a3ded8092987bf0df8ed1a70033ac9
Tx public key: bca1fae3f72f2e531c0af4e09864e1ed2164a042fc272e232910c89264a5d1c7
Timestamp: 1770280168 Timestamp [UTC]: 2026-02-05 08:29:28 Age [y:d:h:m:s]: 00:283:22:46:54
Block: 1471094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208392 RingCT/type: yes/0
Extra: 01bca1fae3f72f2e531c0af4e09864e1ed2164a042fc272e232910c89264a5d1c7021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a45f48499d4d5a7d3d7708211ec47f164b2a5a593bf3a7d2ae99430da83240f 0.000600000000 1960364 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": 1471104, "vin": [ { "gen": { "height": 1471094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a45f48499d4d5a7d3d7708211ec47f164b2a5a593bf3a7d2ae99430da83240f" } } ], "extra": [ 1, 188, 161, 250, 227, 247, 47, 46, 83, 28, 10, 244, 224, 152, 100, 225, 237, 33, 100, 160, 66, 252, 39, 46, 35, 41, 16, 200, 146, 100, 165, 209, 199, 2, 17, 0, 0, 0, 3, 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: