Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e424025921563eb2a388cf22524aaa5d55820fb9dc90da1e7c684ecfbf05824f

Tx prefix hash: 94729219ca261306527519202adc9b3f836fc3a0b41bd81bd32bcbd23918d86a
Tx public key: d25f6c948ce8acd1d1bf195d28070bfb90b832891fb0838bb843321fe66bf5e0
Timestamp: 1745885890 Timestamp [UTC]: 2025-04-29 00:18:10 Age [y:d:h:m:s]: 01:207:09:15:06
Block: 1271658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411836 RingCT/type: yes/0
Extra: 01d25f6c948ce8acd1d1bf195d28070bfb90b832891fb0838bb843321fe66bf5e00211000000061f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 872e46c2ddef15ddd76abc428a2fd8c8761b540869a82f3aa8b31c827c60dc9b 0.000600000000 1758925 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": 1271668, "vin": [ { "gen": { "height": 1271658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "872e46c2ddef15ddd76abc428a2fd8c8761b540869a82f3aa8b31c827c60dc9b" } } ], "extra": [ 1, 210, 95, 108, 148, 140, 232, 172, 209, 209, 191, 25, 93, 40, 7, 11, 251, 144, 184, 50, 137, 31, 176, 131, 139, 184, 67, 50, 31, 230, 107, 245, 224, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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: