Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764558a02654dffa60e2044fcebde83f0fa1439c89a3bc44bc5892db6856884e

Tx prefix hash: 51aa09bb52655e3393a13f1262f525edc0f2cd5da344d1ec7f73c646bf761bf0
Tx public key: d1acbdbf5efa2675cd63970354c5ab156b0eecff51b9920688e10b48f2cba623
Timestamp: 1745597889 Timestamp [UTC]: 2025-04-25 16:18:09 Age [y:d:h:m:s]: 01:018:23:04:47
Block: 1269261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264432 RingCT/type: yes/0
Extra: 01d1acbdbf5efa2675cd63970354c5ab156b0eecff51b9920688e10b48f2cba623021100000004dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e5c156f852d68b6dbb0d5323be3e24dbaaae7b5e190514eef818b538157a4474 0.000600000000 1756496 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": 1269271, "vin": [ { "gen": { "height": 1269261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5c156f852d68b6dbb0d5323be3e24dbaaae7b5e190514eef818b538157a4474" } } ], "extra": [ 1, 209, 172, 189, 191, 94, 250, 38, 117, 205, 99, 151, 3, 84, 197, 171, 21, 107, 14, 236, 255, 81, 185, 146, 6, 136, 225, 11, 72, 242, 203, 166, 35, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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: