Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb20beb35a32f65c1671f27fe699a7cb3112e8b322e9e5e43f4409ebd29026f

Tx prefix hash: 568fd4e86d2e5fadb71fcba42600e318fd671e8b1c459e814a25d5acc19ced18
Tx public key: 526fb8ca29e233c424a981afff6d6f63d7487e2e0d8328ed48d2d75917ac2a6a
Timestamp: 1714311902 Timestamp [UCT]: 2024-04-28 13:45:02 Age [y:d:h:m:s]: 00:200:09:32:26
Block: 1010394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143462 RingCT/type: yes/0
Extra: 01526fb8ca29e233c424a981afff6d6f63d7487e2e0d8328ed48d2d75917ac2a6a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01c621347ca16b47f0b240f8e919afc557064bcd6eee98596d2654d5719d09b6 0.600000000000 1472334 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": 1010404, "vin": [ { "gen": { "height": 1010394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01c621347ca16b47f0b240f8e919afc557064bcd6eee98596d2654d5719d09b6" } } ], "extra": [ 1, 82, 111, 184, 202, 41, 226, 51, 196, 36, 169, 129, 175, 255, 109, 111, 99, 215, 72, 126, 46, 13, 131, 40, 237, 72, 210, 215, 89, 23, 172, 42, 106, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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