Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f340af770d162a4b088f0d93927f6cb408dd8b46c8a6f11739bf8b56d4316bb3

Tx prefix hash: fec250aef7a8bf70f718f089fe9361f26793b0138a1acbb55b4d3e542b7c1000
Tx public key: e155f047a4bc94b6280d17fdb9b4a847d63be9b0f972dd5069b6b1fa6d15e34c
Timestamp: 1708322393 Timestamp [UTC]: 2024-02-19 05:59:53 Age [y:d:h:m:s]: 02:088:07:35:46
Block: 960740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575170 RingCT/type: yes/0
Extra: 01e155f047a4bc94b6280d17fdb9b4a847d63be9b0f972dd5069b6b1fa6d15e34c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b6cc29bf09a278e43aa0b75f3002cbd9cb84e405c5d70a3723135bb2ac76477 0.000600000000 1420327 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": 960750, "vin": [ { "gen": { "height": 960740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b6cc29bf09a278e43aa0b75f3002cbd9cb84e405c5d70a3723135bb2ac76477" } } ], "extra": [ 1, 225, 85, 240, 71, 164, 188, 148, 182, 40, 13, 23, 253, 185, 180, 168, 71, 214, 59, 233, 176, 249, 114, 221, 80, 105, 182, 177, 250, 109, 21, 227, 76, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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: