Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec72eefba9844dc6e0c7b15252d7ca8e2fe2b6df31865a3d12adbd2b504ff2a

Tx prefix hash: 4c407a39dd3c569e934f0dae35ddea188141b517e3c9b41c960cb65af994de52
Tx public key: f50daf080dce009c508f62a9b062d77c5b953c8345439815d0b97f4809eb7616
Timestamp: 1704657658 Timestamp [UTC]: 2024-01-07 20:00:58 Age [y:d:h:m:s]: 02:054:13:52:12
Block: 930334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558649 RingCT/type: yes/0
Extra: 01f50daf080dce009c508f62a9b062d77c5b953c8345439815d0b97f4809eb76160211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ce57509a721ff8302a62661881b98cec2f4f724a3502853149dcb9f93abfd12 0.000600000000 1388216 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": 930344, "vin": [ { "gen": { "height": 930334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce57509a721ff8302a62661881b98cec2f4f724a3502853149dcb9f93abfd12" } } ], "extra": [ 1, 245, 13, 175, 8, 13, 206, 0, 156, 80, 143, 98, 169, 176, 98, 215, 124, 91, 149, 60, 131, 69, 67, 152, 21, 208, 185, 127, 72, 9, 235, 118, 22, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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) | dinastycoin version: tesla-369