Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ce7666ffdd2be97d2b1dfe5fe2612a97bed57568aacbb922f6603bfc5a28510

Tx prefix hash: 0d931b5309a1b78a893ef542ac6c0aaf37255c7ff52bb74decbbd0633e5d0229
Tx public key: 3ff60db75c235ab430dc34a7472443409ce841f93332478e0bbfb115a2ef2ab4
Timestamp: 1721742691 Timestamp [UTC]: 2024-07-23 13:51:31 Age [y:d:h:m:s]: 02:114:19:27:35
Block: 1071992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606798 RingCT/type: yes/0
Extra: 013ff60db75c235ab430dc34a7472443409ce841f93332478e0bbfb115a2ef2ab4021100000006e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e35b2cbeadfae7c2c2d7e364337d9976f7d9296d7bc665d4a638aa3fefb710f 0.000600000000 1544407 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": 1072002, "vin": [ { "gen": { "height": 1071992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e35b2cbeadfae7c2c2d7e364337d9976f7d9296d7bc665d4a638aa3fefb710f" } } ], "extra": [ 1, 63, 246, 13, 183, 92, 35, 90, 180, 48, 220, 52, 167, 71, 36, 67, 64, 156, 232, 65, 249, 51, 50, 71, 142, 11, 191, 177, 21, 162, 239, 42, 180, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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: