Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e25c0c83cf216d23891e31ddbc0dca1879c241ddebb776c7ee2e06034d50bbe5

Tx prefix hash: 2bee5dcd68b290cd01093bd0fe85a404e3653f271c4ac4dfaa23c84d2df9ed11
Tx public key: ccb5953a04854995e8e76081fd91743d8ab9dbb674c193ae11ecd638b2fb73d5
Timestamp: 1714798460 Timestamp [UCT]: 2024-05-04 04:54:20 Age [y:d:h:m:s]: 00:189:02:01:03
Block: 1014439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135352 RingCT/type: yes/0
Extra: 01ccb5953a04854995e8e76081fd91743d8ab9dbb674c193ae11ecd638b2fb73d50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41a4674c80957a51b2be85909a7c6cebc65bd1bcddc31a0f40de0015e78181ca 0.600000000000 1477532 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": 1014449, "vin": [ { "gen": { "height": 1014439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a4674c80957a51b2be85909a7c6cebc65bd1bcddc31a0f40de0015e78181ca" } } ], "extra": [ 1, 204, 181, 149, 58, 4, 133, 73, 149, 232, 231, 96, 129, 253, 145, 116, 61, 138, 185, 219, 182, 116, 193, 147, 174, 17, 236, 214, 56, 178, 251, 115, 213, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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