Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b113065a01eba3a4206df8e1b1df90bbdc6179e033d06c28484b4877deb9cfe

Tx prefix hash: f65ffb3fcebe19ffd832c5e08632e070b3c5071a3fd7e22752476785f9fcd455
Tx public key: caa12760183f89ddaa322394d0c581d470a2ad14c952f7556cac61e9e6259440
Timestamp: 1714164852 Timestamp [UCT]: 2024-04-26 20:54:12 Age [y:d:h:m:s]: 00:347:02:14:13
Block: 1009168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248123 RingCT/type: yes/0
Extra: 01caa12760183f89ddaa322394d0c581d470a2ad14c952f7556cac61e9e625944002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bdc2143c22380581c0b17e1edcd620b50c91251a2cac8337e195d9596732c12 0.600000000000 1470768 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": 1009178, "vin": [ { "gen": { "height": 1009168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bdc2143c22380581c0b17e1edcd620b50c91251a2cac8337e195d9596732c12" } } ], "extra": [ 1, 202, 161, 39, 96, 24, 63, 137, 221, 170, 50, 35, 148, 208, 197, 129, 212, 112, 162, 173, 20, 201, 82, 247, 85, 108, 172, 97, 233, 230, 37, 148, 64, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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