Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41efae5e86ec8f8fa8c17f1b0c29e916e410fa759fecd71ed5678f23a5be621

Tx prefix hash: 01a3e08bf4cee92dd5f0287f64c3a2ecb8beaf5dbc79f814ef9df80538b0699c
Tx public key: 8349a1d04d28fff7394a70828de43b36c095caf2a60e68e9a6666ae831cf771f
Timestamp: 1772114056 Timestamp [UTC]: 2026-02-26 13:54:16 Age [y:d:h:m:s]: 00:261:20:54:28
Block: 1486233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192605 RingCT/type: yes/0
Extra: 018349a1d04d28fff7394a70828de43b36c095caf2a60e68e9a6666ae831cf771f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97aba963a771c5039c3d2f746e89aa1f0ced4e1c567b493dfd11ed3db6f9881d 0.000600000000 1975683 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": 1486243, "vin": [ { "gen": { "height": 1486233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97aba963a771c5039c3d2f746e89aa1f0ced4e1c567b493dfd11ed3db6f9881d" } } ], "extra": [ 1, 131, 73, 161, 208, 77, 40, 255, 247, 57, 74, 112, 130, 141, 228, 59, 54, 192, 149, 202, 242, 166, 14, 104, 233, 166, 102, 106, 232, 49, 207, 119, 31, 2, 17, 0, 0, 0, 1, 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: