Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f20cf803af7a322f2b17f92936e10814e5a2d4010b7420c5e3d64fd018f4dbda

Tx prefix hash: c56f035a9afe9d9da953db892a5c36719712c501941a50a8734318ac643b5789
Tx public key: a67f64cbb764b522f14cb44d98a8f81859a1b92297a07faff9805c7f60798598
Timestamp: 1742390467 Timestamp [UTC]: 2025-03-19 13:21:07 Age [y:d:h:m:s]: 01:240:23:53:22
Block: 1242731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436189 RingCT/type: yes/0
Extra: 01a67f64cbb764b522f14cb44d98a8f81859a1b92297a07faff9805c7f607985980211000000051db82ba9000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9f5e7913a8921bb4071de2e30e4bce49f239db4827cf361adf8a57a723f289e5 0.000600000000 1729706 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": 1242741, "vin": [ { "gen": { "height": 1242731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f5e7913a8921bb4071de2e30e4bce49f239db4827cf361adf8a57a723f289e5" } } ], "extra": [ 1, 166, 127, 100, 203, 183, 100, 181, 34, 241, 76, 180, 77, 152, 168, 248, 24, 89, 161, 185, 34, 151, 160, 127, 175, 249, 128, 92, 127, 96, 121, 133, 152, 2, 17, 0, 0, 0, 5, 29, 184, 43, 169, 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: