Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030f721fd9d0a00a191a3b917e4f3c0646711c36ca020029a6f437171e66b998

Tx prefix hash: adc63a91d272305920095218bb8f6e28a57586ee2bd970206b83e30bd2b6408f
Tx public key: ed474327b548a0760fa111b9f623e64373f9b5ec9806c11ae91c365aea468539
Timestamp: 1742249684 Timestamp [UTC]: 2025-03-17 22:14:44 Age [y:d:h:m:s]: 01:244:13:54:29
Block: 1241559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438808 RingCT/type: yes/0
Extra: 01ed474327b548a0760fa111b9f623e64373f9b5ec9806c11ae91c365aea4685390211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0fbc709145ca16c7c3a2dfce051139edf7700f7ada3339cc1f59bd2e0b1fc85 0.000600000000 1728532 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": 1241569, "vin": [ { "gen": { "height": 1241559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0fbc709145ca16c7c3a2dfce051139edf7700f7ada3339cc1f59bd2e0b1fc85" } } ], "extra": [ 1, 237, 71, 67, 39, 181, 72, 160, 118, 15, 161, 17, 185, 246, 35, 230, 67, 115, 249, 181, 236, 152, 6, 193, 26, 233, 28, 54, 90, 234, 70, 133, 57, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: