Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12507f7930dab175d6d95c81eba2f3a1375d879b75970fe3f92f8093fe29b90e

Tx prefix hash: 8d3ce7bc23ef4eb9165fdf2abe7e936509aa41462586cf78bd50697cbd63e482
Tx public key: 7d9fa81d1e6de7c9bd95be285c054834659f00aca5f6e2f29bba3a1ff5fa998a
Timestamp: 1750105665 Timestamp [UTC]: 2025-06-16 20:27:45 Age [y:d:h:m:s]: 00:330:17:46:02
Block: 1306476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226417 RingCT/type: yes/0
Extra: 017d9fa81d1e6de7c9bd95be285c054834659f00aca5f6e2f29bba3a1ff5fa998a02110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 478c8623053253a081417e15141d88e014bdc05d915e33d9080daf24b67749f1 0.000600000000 1794083 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": 1306486, "vin": [ { "gen": { "height": 1306476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "478c8623053253a081417e15141d88e014bdc05d915e33d9080daf24b67749f1" } } ], "extra": [ 1, 125, 159, 168, 29, 30, 109, 231, 201, 189, 149, 190, 40, 92, 5, 72, 52, 101, 159, 0, 172, 165, 246, 226, 242, 155, 186, 58, 31, 245, 250, 153, 138, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: