Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516eb03280fa119a4b0527f84a6f0a845d97093ba891fde0d9357b81aca37b72

Tx prefix hash: 31ee51f7c4ab195e993f77f589c3f8ecd81ea0e30ded48d0b8c97125e539ea2a
Tx public key: 0f092ff324adf7385b413fd0fa32e3d92c72caa51ec051d41c1a7fc4171e18b8
Timestamp: 1742181336 Timestamp [UTC]: 2025-03-17 03:15:36 Age [y:d:h:m:s]: 01:057:10:58:11
Block: 1240985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291907 RingCT/type: yes/0
Extra: 010f092ff324adf7385b413fd0fa32e3d92c72caa51ec051d41c1a7fc4171e18b8021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01123f1349698ef7d31c3973e044032cf8d479eb6b8df5e3a0d64db769c5ca0f 0.000600000000 1727958 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": 1240995, "vin": [ { "gen": { "height": 1240985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01123f1349698ef7d31c3973e044032cf8d479eb6b8df5e3a0d64db769c5ca0f" } } ], "extra": [ 1, 15, 9, 47, 243, 36, 173, 247, 56, 91, 65, 63, 208, 250, 50, 227, 217, 44, 114, 202, 165, 30, 192, 81, 212, 28, 26, 127, 196, 23, 30, 24, 184, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: