Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0d487c8024ceaec257408f167aaf0efaf64da3315306dc47a154a917f39941

Tx prefix hash: 7f8be5fbad1c541fcf7d5dcd1ec9f3d7dbebb842cb6ed0ed9d00665ea8408d5b
Tx public key: e2bbe4ad2d02ad59c00e843490aaf36e9b43b0231a57a32f29db7b1189e1cf27
Timestamp: 1693298558 Timestamp [UTC]: 2023-08-29 08:42:38 Age [y:d:h:m:s]: 02:261:13:32:18
Block: 836361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699044 RingCT/type: yes/0
Extra: 01e2bbe4ad2d02ad59c00e843490aaf36e9b43b0231a57a32f29db7b1189e1cf270211000000043c9a4d68000000000000000000

1 output(s) for total of 0.001039414794 xmr

stealth address amount amount idx tag
00: 2c84b1a6bd06e07ea22bdc488fa5b8e5d8d5d03861049569d1edbce1a8eca3fc 0.001039414794 1288945 of 0 -

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": 836371, "vin": [ { "gen": { "height": 836361 } } ], "vout": [ { "amount": 1039414794, "target": { "key": "2c84b1a6bd06e07ea22bdc488fa5b8e5d8d5d03861049569d1edbce1a8eca3fc" } } ], "extra": [ 1, 226, 187, 228, 173, 45, 2, 173, 89, 192, 14, 132, 52, 144, 170, 243, 110, 155, 67, 176, 35, 26, 87, 163, 47, 41, 219, 123, 17, 137, 225, 207, 39, 2, 17, 0, 0, 0, 4, 60, 154, 77, 104, 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: