Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e3ff5c1b6b390c2b650c0f617a9a0c4bc4c6295614b9341892a29c8251e5dbf

Tx prefix hash: 87d0debe09700e42bbcabcf76edd58eab890e4a1332226020261e1e3c45db4ed
Tx public key: 59e3eb53a5c704875379a916d06d552b9595ec0e3b38d9719bf1f58e21d6bf2d
Timestamp: 1709413344 Timestamp [UCT]: 2024-03-02 21:02:24 Age [y:d:h:m:s]: 00:339:21:10:07
Block: 969792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243018 RingCT/type: yes/0
Extra: 0159e3eb53a5c704875379a916d06d552b9595ec0e3b38d9719bf1f58e21d6bf2d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc523cb33796dae880506efe1124e97531273faba13adbb0914b908988191f35 0.600000000000 1429637 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": 969802, "vin": [ { "gen": { "height": 969792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc523cb33796dae880506efe1124e97531273faba13adbb0914b908988191f35" } } ], "extra": [ 1, 89, 227, 235, 83, 165, 199, 4, 135, 83, 121, 169, 22, 208, 109, 85, 43, 149, 149, 236, 14, 59, 56, 217, 113, 155, 241, 245, 142, 33, 214, 191, 45, 2, 17, 0, 0, 0, 4, 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