Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 261e5a5499e302d0a13bc7a0f13687ce0f545adf016d53c66a6706d4d0ec406c

Tx prefix hash: 86da41600fa5160e9f083ad122e780efe779f1cd9a6ea7b065a4b626eca64543
Tx public key: 1933d566e5b882481e0b96c9437b5ee49386fa26272ef9a8c178a2218ea7f4cb
Timestamp: 1707030666 Timestamp [UCT]: 2024-02-04 07:11:06 Age [y:d:h:m:s]: 00:340:20:45:53
Block: 950016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244037 RingCT/type: yes/0
Extra: 011933d566e5b882481e0b96c9437b5ee49386fa26272ef9a8c178a2218ea7f4cb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f35627b0cb82048e10562ea84b32cbe5aa29187e8a93f2344e80a902d6068ea 0.600000000000 1408560 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 dinasty-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": 950026, "vin": [ { "gen": { "height": 950016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f35627b0cb82048e10562ea84b32cbe5aa29187e8a93f2344e80a902d6068ea" } } ], "extra": [ 1, 25, 51, 213, 102, 229, 184, 130, 72, 30, 11, 150, 201, 67, 123, 94, 228, 147, 134, 250, 38, 39, 46, 249, 168, 193, 120, 162, 33, 142, 167, 244, 203, 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): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8