Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e158a92728b4f3f4c115100201393d9b2edecd4314647da6b19f9836a04663c

Tx prefix hash: 3be14a93f8becd6c0e82719918da50b9564cc5710e76ea301a2b2529e2da2c0f
Tx public key: cca4a76943f9e1d161743004144e86c07a1e7fbfe5535d522223a905c7bc09a6
Timestamp: 1716320491 Timestamp [UCT]: 2024-05-21 19:41:31 Age [y:d:h:m:s]: 00:317:06:17:08
Block: 1027053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226748 RingCT/type: yes/0
Extra: 01cca4a76943f9e1d161743004144e86c07a1e7fbfe5535d522223a905c7bc09a602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ac28f3bdd18f6b24194f745aee02bbca763d5a3ba99bb89895edf79d6b36990 0.600000000000 1494472 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": 1027063, "vin": [ { "gen": { "height": 1027053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ac28f3bdd18f6b24194f745aee02bbca763d5a3ba99bb89895edf79d6b36990" } } ], "extra": [ 1, 204, 164, 167, 105, 67, 249, 225, 209, 97, 116, 48, 4, 20, 78, 134, 192, 122, 30, 127, 191, 229, 83, 93, 82, 34, 35, 169, 5, 199, 188, 9, 166, 2, 17, 0, 0, 0, 2, 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