Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f9e338d5547f4aeb06bbcd0babf08af94ec6278886a5702955660eb8adf719d

Tx prefix hash: f61528283dace256bca513904b1fd6cd68cf94168004b1e373ffc2a6a9c0fa63
Tx public key: 6a011a5527a1ed2a3dddb3fdbe94e9d54c7eac12c4184626a9c07c4ac351649e
Timestamp: 1705800363 Timestamp [UCT]: 2024-01-21 01:26:03 Age [y:d:h:m:s]: 01:034:21:45:49
Block: 939793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286025 RingCT/type: yes/0
Extra: 016a011a5527a1ed2a3dddb3fdbe94e9d54c7eac12c4184626a9c07c4ac351649e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d641c76d5cbf8c7125cb5fe8b6afe9594c3156bc8d6e26b350cbc4c4321988fb 0.600000000000 1397925 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": 939803, "vin": [ { "gen": { "height": 939793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d641c76d5cbf8c7125cb5fe8b6afe9594c3156bc8d6e26b350cbc4c4321988fb" } } ], "extra": [ 1, 106, 1, 26, 85, 39, 161, 237, 42, 61, 221, 179, 253, 190, 148, 233, 213, 76, 126, 172, 18, 196, 24, 70, 38, 169, 192, 124, 74, 195, 81, 100, 158, 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