Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8fd8b529eaa52f93a1484c4d4df8e106aed53524b7bd8353de9665ea10b18f

Tx prefix hash: 9c98d51c6ba7de64681dc4506e62fa7d7e71f3f751d2857a831d9fed33dfbcc0
Tx public key: 730f283847bc46f4a0a0ba5b31dee5280b6b20d64eca71e3f42cf22e3489fe64
Timestamp: 1786689084 Timestamp [UTC]: 2026-08-14 06:31:24 Age [y:d:h:m:s]: 00:096:07:59:24
Block: 1612949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 68240 RingCT/type: yes/0
Extra: 01730f283847bc46f4a0a0ba5b31dee5280b6b20d64eca71e3f42cf22e3489fe64

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6e2cfc5dafe0f9df68614c995beb74c5a4fc9fefc0033b063ad54f1d4f5161e5 0.000600000000 2102969 of 15 <6e>

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": 1612959, "vin": [ { "gen": { "height": 1612949 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6e2cfc5dafe0f9df68614c995beb74c5a4fc9fefc0033b063ad54f1d4f5161e5", "view_tag": "6e" } } } ], "extra": [ 1, 115, 15, 40, 56, 71, 188, 70, 244, 160, 160, 186, 91, 49, 222, 229, 40, 11, 107, 32, 214, 78, 202, 113, 227, 244, 44, 242, 46, 52, 137, 254, 100 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: